• docs(review): apply Tristan's two must-fix items from the final review #97 👈 (View in Graphite)
• docs(review): address Greptile review feedback across the stack #96
• docs(feedback): apply Tristan's revisions from RequestNetwork/request-api#806 #95
• docs(kyt): document KYT-screened payments as a use case + payee-destination field #94
• docs(secure-payments): document redirectUrl + redirectLabel #93
• docs(verify): fix broken cross-refs surfaced by mintlify broken-links #92
• docs(scripts): add Playwright screenshot capture scaffolding #91
• docs(content): add use-case pages, Dashboard + Secure Payment tools pages #90
• docs(content): refresh Tron coverage, batch-payment EVM scope, webhook 12-event list #89
• docs(nav): restructure navigation, remove legacy pages, retire Portal #88
• docs: fix broken links and clarify edge cases #87
• docs: add missing feature documentation for recent API changes #86
• docs: fix implementation discrepancies across API docs #85
• docs: remove beta banner and legacy SDK tab #78
• Remove AI-generated content warnings and update internal links #77
• docs(lifecycle): replace external image with local asset and remove AI-generated warning #76
• docs: remove AI-generated content warnings and simplify Request Scan page #75
• docs(resources): remove community page from navigation #74
• docs(supported-chains): add Tron network support and enhance currency documentation #73
• docs(supported-chains): streamline supported chains and currencies documentation #72
• docs(api-reference): add v2 endpoints overview and switch docs OpenAPI to v2-only spec Improve API Reference navigation by introducing a dedicated Endpoints Overview page in docs and wiring Mintlify OpenAPI rendering to a local v2-only spec. - add `api-re #71
• docs(authentication): simplify auth guide with API key vs Client ID methods and remove AI-generated content #70
• docs(fee-breakdowns): rewrite to focus on API response locations and reconciliation usage #69
• docs(protocol-fees): add protocol fees documentation and navigation #68
• docs(platform-fees): simplify configuration guide and remove AI-generated content warning #67
• docs(query-payments): rewrite with practical implementation focus and remove AI warning #66
• docs(query-requests): simplify and refactor query requests documentation for practical implementation #65
• docs(payment-detection): simplify content and remove AI warning #64
• docs(partial-payments): rewrite with step-by-step implementation guide and clarify API usage #63
• docs(standard-payments): remove AI warning, restructure content with step-by-step flow, and update API references #62
• docs(conversion-payments): rewrite with step-by-step implementation guide and remove AI-generated warning #61
• docs(payment-types): simplify overview and add payment type selection guidance #60
• docs(crypto-to-fiat): expand comprehensive guide with sandbox access, compliance flows, and implementation details #59
• docs(recurring-payments): rewrite with comprehensive workflow, security details, and practical implementation guide #58
• docs(batch-payments): add comprehensive implementation guide with examples, workflow diagrams, and demo videos #57
• docs(crosschain-payments): replace AI-generated content with comprehensive implementation guide #56
• docs(create-requests): rewrite with workflows, examples, and remove AI warning #55
• feat: add complete integration tutorial with Node.js backend and React frontend #54
• docs(getting-started): remove AI warning and refactor to focus on practical payment integration #53
• docs(api-portal): remove AI warning, add local screenshot, and update .gitignore #52
• docs: remove release notes section and streamline use cases to core features #51
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Greptile Summary

This PR applies two accuracy fixes identified in a final review: aligning the SIWE message example in the wallet-authentication docs with actual server output, and adding a payment-destination prerequisite to the Client ID generation steps.

• api-reference/wallet-authentication.mdx: The example message string now ends with a period ("Sign in to Request Network."), removes the Chain ID: 1 line the server does not emit, and appends Expiration Time (using the same ISO timestamp already shown in expiresAt).
• api-setup/getting-started.mdx: A new step 2 explicitly tells users to create a payment destination first, since the Client IDs section only appears after one exists. Subsequent steps are renumbered, and the button label distinguishes between the first-time empty-state ("Generate your first Client ID") and subsequent creation ("Generate New Client ID").

Confidence Score: 5/5

Safe to merge — both changes are documentation-only accuracy corrections with no functional code impact.

Both files contain only documentation text changes. The SIWE message update brings the example into sync with the real server output (period, no Chain ID, Expiration Time field), and the getting-started update adds a clearly missing prerequisite step that prevents user confusion at the dashboard. Neither change introduces incorrect information or breaks any existing guidance.

No files require special attention. The top-level Quick Setup Steps block in getting-started.mdx still omits the payment-destination prerequisite, but this was flagged in a prior review and does not block this PR.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant User
    participant Dashboard
    participant AuthAPI as auth.request.network
    participant Wallet

    User->>Dashboard: Sign up / Log in
    User->>Dashboard: Set up payment destination
    Dashboard-->>User: Destination created (Client IDs section now visible)
    User->>Dashboard: Open Manage Destination → Client IDs
    User->>Dashboard: Click "Generate your first Client ID"
    Dashboard-->>User: Client ID issued

    Note over User,AuthAPI: Wallet Auth (SIWE) Flow
    User->>AuthAPI: "POST /v1/auth/wallet/challenge {address}"
    AuthAPI-->>User: "{challengeId, nonce, message, expiresAt}"
    Note right of AuthAPI: message includes: Sign in to Request Network. No Chain ID field. Expiration Time = expiresAt
    User->>Wallet: Sign message
    Wallet-->>User: signature
    User->>AuthAPI: "POST /v1/auth/wallet/verify {challengeId, nonce, message, signature}"
    AuthAPI-->>User: httpOnly session cookie

_{Reviews (2): Last reviewed commit: "docs(review): apply Tristan's two must-f..." | Re-trigger Greptile}

Merge activity

• May 12, 4:02 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• May 12, 5:24 PM UTC: Graphite rebased this pull request as part of a merge.
• May 12, 5:25 PM UTC: @rodrigopavezi merged this pull request with Graphite.